home *** CD-ROM | disk | FTP | other *** search
GLBD(1) User Commands GLBD(1) NNNNAAAAMMMMEEEE ggggllllbbbbdddd - Global Location Broker Daemon SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS ////eeeettttcccc////nnnnccccssss////ggggllllbbbbdddd [ ----ccccrrrreeeeaaaatttteeee { ----ffffiiiirrrrsssstttt [ ----ffffaaaammmmiiiillllyyyy _f_a_m_i_l_y__n_a_m_e ] | ---- ffffrrrroooommmm _h_o_s_t__n_a_m_e } ] [ ----cccchhhhaaaannnnggggeeee____ffffaaaammmmiiiillllyyyy _f_a_m_i_l_y__n_a_m_e ] [ ----lllliiiisssstttteeeennnn _f_a_m_i_l_y__l_i_s_t ] [ ---- vvvveeeerrrrssssiiiioooonnnn ] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN The Global Location Broker (GLB), part of the Network Com- puting System (NCS), helps clients to locate servers on a network or internet. The GLB database stores the locations (that is, the network addresses and port numbers) where server processes are running. A daemon maintains this data- base and provides access to it. There are two versions of the GLB daemon: ggggllllbbbbdddd and nnnnrrrrggggllllbbbbdddd. We provide the replicatable version, ggggllllbbbbdddd, only for Apollo, SunOS, and ULTRIX systems. For other systems, we provide the non-replicatable version, nnnnrrrrggggllllbbbbdddd. Here, we describe only ggggllllbbbbdddd. You can replicate the GLB database to increase its availa- bility. Copies of the database can exist on several hosts, with a ggggllllbbbbdddd running on each of those hosts to maintain the consistency of the database replicas. (In an internet, at least one ggggllllbbbbdddd must run in each network.) Each replica of the GLB keeps a list of all the other GLB replicas. The ddddrrrrmmmm____aaaaddddmmmmiiiinnnn tool administers the replication of the GLB data- base and of the replica list. Currently, ggggllllbbbbdddd supports both the DARPA IP and Domain DDS network protocols. A GLB replica can allow access to its database from both IP and DDS clients. However, when com- municating with each other to maintain replication of the GLB database, GLB replicas should use only one protocol fam- ily. You choose which family the GLBs will use. In an internet, all routing nodes must support this family. If a set of GLB replicas includes any SunOS or ULTRIX sys- tems, all replicas must use IP protocols to communicate with each other. A replica running on an Apollo system can com- municate with other replicas via IP protocols but still pro- vide lookup and update services to its clients via both IP and DDS protocols. The following subsections briefly describe ggggllllbbbbdddd startup on various systems. See _M_a_n_a_g_i_n_g _N_C_S _S_o_f_t_w_a_r_e for more detailed information. NCS Administration Last change: 1 GLBD(1) User Commands GLBD(1) RRRRuuuunnnnnnnniiiinnnngggg ggggllllbbbbdddd oooonnnn SSSSRRRR11110000 AAAAppppoooolllllllloooo SSSSyyyysssstttteeeemmmmssss If the GLB is to communicate via IP protocols, either with clients or with other GLB replicas, a TCP daemon (ttttccccppppdddd) must be running on the local host when ggggllllbbbbdddd is started. Also, regardless of which protocol ggggllllbbbbdddd uses, a Local Location Broker daemon (llllllllbbbbdddd) must be running on the local host when ggggllllbbbbdddd is started. The TCP and Location Broker daemons should be started in this order: ttttccccppppdddd, llllllllbbbbdddd, ggggllllbbbbdddd. The daemons will start automatically in the correct order at boot time if the files ////eeeettttcccc////ddddaaaaeeeemmmmoooonnnnssss////ttttccccppppdddd, ////eeeettttcccc////ddddaaaaeeeemmmmoooonnnnssss////llllllllbbbbdddd, and ////eeeettttcccc////ddddaaaaeeeemmmmoooonnnnssss////ggggllllbbbbdddd exist. Use ttttoooouuuucccchhhh or ccccrrrrffff to create these files. RRRRuuuunnnnnnnniiiinnnngggg ggggllllbbbbdddd oooonnnn SSSSRRRR9999 AAAAppppoooolllllllloooo SSSSyyyysssstttteeeemmmmssss If the GLB is to communicate via IP protocols, either with clients or with other GLB replicas, a TCP server (ttttccccpppp____sssseeeerrrrvvvveeeerrrr) must be running on the local host when ggggllllbbbbdddd is started. Also, regardless of which protocol ggggllllbbbbdddd uses, a Local Location Broker daemon (llllllllbbbbdddd) must be running on the local host when ggggllllbbbbdddd is started. The TCP server and the Location Broker daemons should be started in this order: ttttccccpppp____sssseeeerrrrvvvveeeerrrr, llllllllbbbbdddd, ggggllllbbbbdddd. Typically, processes are started by the file ````nnnnooooddddeeee____ddddaaaattttaaaa////ssssttttaaaarrrrttttuuuupppp...._s_u_f_f_i_x, where _s_u_f_f_i_x indicates the display type. RRRRuuuunnnnnnnniiiinnnngggg ggggllllbbbbdddd oooonnnn SSSSuuuunnnnOOOOSSSS aaaannnndddd UUUULLLLTTTTRRRRIIIIXXXX SSSSyyyysssstttteeeemmmmssss On SunOS and ULTRIX systems, the GLB communicates only via IP protocols. A Local Location Broker daemon (llllllllbbbbdddd) must be running on the local host when ggggllllbbbbdddd is started. Typically, the llllllllbbbbdddd and ggggllllbbbbdddd processes are started in back- ground at boot time from ////eeeettttcccc////rrrrcccc. If you start the daemons by hand, you must be root. OOOOPPPPTTTTIIIIOOOONNNNSSSS ----ccccrrrreeeeaaaatttteeee Create a replica of the GLB. This option creates a GLB database in addition to starting a broker process. It must be used with either ----ffffiiiirrrrsssstttt or ---- ffffrrrroooommmm. ----ffffiiiirrrrsssstttt This option can be used only with the ---- ccccrrrreeeeaaaatttteeee option. Use it to create the first replica (that is, the very first instance) of the GLB on your network or internet. ----ffffaaaammmmiiiillllyyyy _f_a_m_i_l_y__n_a_m_e This option can be used only in conjunction with the ----ffffiiiirrrrsssstttt option. It specifies the address fam- ily that the first GLB replica will use to iden- tify itself on the replica list. Any subsequently NCS Administration Last change: 2 GLBD(1) User Commands GLBD(1) created replicas must use this family to communi- cate with this replica. Currently, _f_a_m_i_l_y__n_a_m_e can be either ddddddddssss or iiiipppp. If this option is not used, the replica will be identified on the replica list by its DDS address. ----ffffrrrroooommmm _h_o_s_t__n_a_m_e This option can be used only with the ---- ccccrrrreeeeaaaatttteeee option. Use it to create additional replicas of the GLB. A replica of the GLB must exist at _h_o_s_t__n_a_m_e. The database and replica list for the new replica are initialized from those at _h_o_s_t__n_a_m_e. The replica at _h_o_s_t__n_a_m_e adds an entry for the new replica to its replica list and pro- pagates the entry to the other GLB replicas. A _h_o_s_t__n_a_m_e takes the form _f_a_m_i_l_y::::_h_o_s_t, where the host can be specified either by its name or by its network address. For example, ddddddddssss::::////////jjjjeeeeeeeevvvveeeessss, ddddddddssss::::####999955559999aaaa....999944440000ffff, iiiipppp::::bbbbeeeerrrrttttiiiieeee, and iiiipppp::::####111199992222....5555....5555....5555 are acceptable host names. The new replica will use the same address family as _h_o_s_t__n_a_m_e in identifying itself on the replica list. For example, if _h_o_s_t__n_a_m_e is an IP address, the new replica will be listed by its IP address on the replica list. ----cccchhhhaaaannnnggggeeee____ffffaaaammmmiiiillllyyyy _f_a_m_i_l_y__n_a_m_e Use this option only if network reconfigurations require that you change the address family of every GLB replica; see the discussion in the sec- tion. Currently, _f_a_m_i_l_y__n_a_m_e can be either ddddddddssss or iiiipppp. For a procedure to change all of your GLB replicas from one address family to another, see _M_a_n_a_g_i_n_g _N_C_S _S_o_f_t_w_a_r_e. ----lllliiiisssstttteeeennnn _f_a_m_i_l_y__l_i_s_t This option restricts the address families on which a GLB listens. Use it only if you are creating a special configuration where access to a GLB is restricted to a subset of hosts in the net- work or internet. The _f_a_m_i_l_y__l_i_s_t is a list of the address families on which the GLB will listen. Names in this list are separated by spaces. Possible family names include ddddddddssss and iiiipppp. The GLB will always listen for requests from the NCS Administration Last change: 3 GLBD(1) User Commands GLBD(1) family by which it is listed on the replica list, even if that family is not specified in _f_a_m_i_l_y__l_i_s_t. If ggggllllbbbbdddd is started without the ----lllliiiisssstttteeeennnn option, the GLB will listen on all address families that are supported both by NCS and by the local host. On Apollo systems, this set of families always includes ddddddddssss and may also include iiiipppp. On most other systems, iiiipppp is currently the only family. ----vvvveeeerrrrssssiiiioooonnnn Display the version of NCK that this ggggllllbbbbdddd belongs to, but do not start the daemon. EEEEXXXXAAAAMMMMPPPPLLLLEEEESSSS 1. Create and start for the first time the first replica of the GLB on this network or internet: _$$$$ ////eeeettttcccc////sssseeeerrrrvvvveeeerrrr ////eeeettttcccc////nnnnccccssss////ggggllllbbbbdddd ----ccccrrrreeeeaaaatttteeee ----ffffiiiirrrrsssstttt ----ffffaaaammmmiiiillllyyyy ddddddddssss &&&& 2. Start for the first time a subsequent replica of the GLB, initializing its database from host ////////jjjjeeeeeeeevvvveeeessss: _$$$$ ////eeeettttcccc////sssseeeerrrrvvvveeeerrrr ////eeeettttcccc////nnnnccccssss////ggggllllbbbbdddd ----ccccrrrreeeeaaaatttteeee ----ffffrrrroooommmm ddddddddssss::::////////jjjjeeeeeeeevvvveeeessss &&&& 3. Restart an existing replica of the GLB: _$$$$ ////eeeettttcccc////sssseeeerrrrvvvveeeerrrr ////eeeettttcccc////nnnnccccssss////ggggllllbbbbdddd &&&& 4. Restart an existing replica of the GLB on remote host ////////bbbbeeeerrrrttttiiiieeee: _$$$$ ccccrrrrpppp ---- oooonnnn ////////bbbbeeeerrrrttttiiiieeee ////eeeettttcccc////sssseeeerrrrvvvveeeerrrr ////////bbbbeeeerrrrttttiiiieeee////eeeettttcccc////nnnnccccssss////ggggllllbbbbdddd &&&& FFFFIIIILLLLEEEESSSS On Apollo systems, ggggllllbbbbdddd writes diagnostic output to the file ```` nnnnooooddddeeee____ddddaaaattttaaaa////ssssyyyysssstttteeeemmmm____llllooooggggssss////ggggllllbbbb____lllloooogggg. On other UNIX systems, the log file is ////eeeettttcccc////nnnnccccssss////ggggllllbbbb____lllloooogggg. SSSSEEEEEEEE AAAALLLLSSSSOOOO _M_a_n_a_g_i_n_g _N_C_S _S_o_f_t_w_a_r_e NCS Administration Last change: 4 
